49 research outputs found

    Seizing the Potentialities of Open Science: From a Community to a Platform Journal

    Get PDF
    The adventure of the Research Group on Collaborative Spaces (RGCS)[1] started in March 2014. At that time, our network was not an association. It was a Working Group settled in France, in the UK and in Canada gathering researchers and practitioners interested in topics of new collaborative work and collaborative spaces[2]. Quickly came on the way the issue of Open Science (OS) and Citizen Sciences. To develop knowledge commons (for society and organizations) and to explore impactful, inclusive, responsible, resonant new practices, methods and concepts about and for collaborative practices, OS appeared quickly as a promising spac

    Implementation of weakly structured systems: moving from local practices to common organizational rules

    Get PDF
    The traditional implementation of an information system assumes that the IT system to be implemented is highly structured (HSS), carrying out regulatory functions expressed in organizational rules scripted into the system. Subsequent implementation seeks users’ compliance with stated regulatory needs. We propose an alternative view of implementing IT systems when such systems are weakly structured (WSS). In these systems, most scripted rules express the composition and behavior of digital objects, which organizational members tend to voluntarily enact as part of their tasks. By using analytical inference and illustrative examples, this work extends the Trifecta model of organizational regulation by developing a vocabulary and a process model for the evolution of the rule system during the implementation of WSS. The offered model depicts IT implementation as a movement from local practices, where system uses are discovered as affordances, to wider rule sets that regulate and enforce the shared deployment of such affordances

    Cohomological tautness for Riemannian foliations

    Full text link
    In this paper we present some new results on the tautness of Riemannian foliations in their historical context. The first part of the paper gives a short history of the problem. For a closed manifold, the tautness of a Riemannian foliation can be characterized cohomologically. We extend this cohomological characterization to a class of foliations which includes the foliated strata of any singular Riemannian foliation of a closed manifold

    Tautness for riemannian foliations on non-compact manifolds

    Full text link
    For a riemannian foliation F\mathcal{F} on a closed manifold MM, it is known that F\mathcal{F} is taut (i.e. the leaves are minimal submanifolds) if and only if the (tautness) class defined by the mean curvature form κμ\kappa_\mu (relatively to a suitable riemannian metric μ\mu) is zero. In the transversally orientable case, tautness is equivalent to the non-vanishing of the top basic cohomology group Hn(M/F)H^{^{n}}(M/\mathcal{F}), where n = \codim \mathcal{F}. By the Poincar\'e Duality, this last condition is equivalent to the non-vanishing of the basic twisted cohomology group Hκμ0(M/F)H^{^{0}}_{_{\kappa_\mu}}(M/\mathcal{F}), when MM is oriented. When MM is not compact, the tautness class is not even defined in general. In this work, we recover the previous study and results for a particular case of riemannian foliations on non compact manifolds: the regular part of a singular riemannian foliation on a compact manifold (CERF).Comment: 18 page

    Code Reuse in Open Source Software

    Get PDF
    Code reuse is a form of knowledge reuse in software development that is fundamental to innovation in many fields. However, to date there has been no systematic investigation of code reuse in open source software projects. This study uses quantitative and qualitative data gathered from a sample of six open source software projects to explore two sets of research questions derived from the literature on software reuse in firms and open source software development. We find that code reuse is extensive across the sample and that open source software developers, much like developers in firms, apply tools that lower their search costs for knowledge and code, assess the quality of software components, and have incentives to reuse code. Open source software developers reuse code because they want to integrate functionality quickly, because they want to write preferred code, because they operate under limited resources in terms of time and skills, and because they can mitigate development costs through code reuse
    corecore